home *** CD-ROM | disk | FTP | other *** search
- Hints and Tips
- 8.8
- CC Turbo Driver v4 − I’d like to pass on to other Archive readers some
- answers that I received from CC.
- 8.8
- 1) The command *Printer$BlackScale is no longer supported by the v4
- TurboDrivers; instead, CC offer “sophisticated colour correction
- tables”; those for HP printers are “shortly” to be released.
- 8.8
- 2) The Turbo module which could be used in earlier versions of the TD to
- enable other printer drivers to use the dongled cable has been replaced
- by the program !PrintQFS, which is cunningly hidden within
- !System.!CCShared.
- 8.8
- By the way, CC informed me that Style has reached version 3.07. Free
- upgrades from v. 3.04 can be obtained in the usual way − by sending in
- master disk 1. (Don’t forget to send the return postage!)
- 8.8
- Jochen Konietzko, Köln, Germany u
- 8.8
- Fireworkz Pro − I reported some problems with version 1.20 to Colton
- Software and was told (in a letter dated 15th March) that the latest
- version, 1.20/50, fixes most of these problems. Version 1.21 “is due out
- in about three weeks”. (Colton are currently saying, “it will be
- available during April”. Ed) The upgrade procedure here is to send in
- both program disks − don’t forget − return postage!
- 8.8
- Jochen Konietzko, Köln, Germany u
- 8.8
- Printing from text editors − I mentioned, in my review of lottery
- packages, that one of them would not print on my LaserDirect, because it
- ‘prints’ to a null file instead of to the printer. I have now stopped
- trying to use Zap for the same reason. If I drag a text file to the
- printer icon (with Zap installed instead of Edit), it prints properly
- but if I try to print the document currently displayed on the screen, it
- does not. I don’t know whether this is a general problem or whether I
- have overlooked some control parameter.
- 8.8
- Colin Singleton, Sheffield u
- 8.8
- Many text editors, including both Edit and Zap, cheat when you try to
- print and send the data directly to the parallel port. This is fine if
- you have a standard printer, but if you use a different connection (e.g.
- serial or laser direct), the file will not be printed. Also, if you use
- a Turbo Driver, it is circumvented by Edit, so the text is corrupted.
- There are a couple of ways around this.
- 8.8
- You can save to a file and drag that to the printer icon, or try
- dragging the file from the save box to the print icon. This should have
- the same result and it means that you don’t have to delete the file
- afterwards. With Zap, you can also press <shift-print> rather than
- <print> which will force the printout to go via the printer driver.
- Since Zap allows you to reconfigure the keyboard shortcuts, you can set
- <print> to print via the printer driver. (Choose Edit keys from the
- options submenu, find the print keymapping which, by default, will be
- set to Quickprint and change it to Printfile. Save the keys file and
- choose Reload keys again, from the options submenu for the change to
- take effect).
- 8.8
- Matthew Hunter, NCS u
- 8.8
- Wolfenstein bugs − A few days after I had sent my Wolfenstein hint
- (Archive 8.7, p.12) to Paul, I found that sometimes the saved files
- remained open even though the !Cfs.!Run file was not. I turned to
- PowerSlave for help and this is what Eddie Edwards told me:
- 8.8
- There is a bug in Wolfenstein’s code which means that the files are only
- closed when the current directory is on the same filing system as
- Wolfenstein. Since I use ADFS and SCSI, this would often not be the
- case.
- 8.8
- The recommended remedy is to add, at the start of the !Run file, a
- Dir<Obey$Dir> command.
- 8.8
- This fix seems to work perfectly.
- 8.8
- Another problem I have is that Wolfenstein always kills my computer’s
- beep. This bug can be fixed by adding:
- 8.8
- Channelvoice 1 MyVoice
- 8.8
- to the end of the !Run file.
- 8.8
- Jochen Konietzko, Köln, Germany u
- From COmment COlumn
- Turbo Drivers (not a) problem − The problem of Printers 1.28 with the
- current versions of the Turbo Drivers has, apparently, now been fixed,
- so please do not remove line 91 (as we stated in Archive 8.7 p13) of the
- !RunImage file! If you still have a problem, contact Computer Concepts.
- 8.8
- CC Technical Support u
-